-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Sectors] Non-abelian fusion #1363
base: main
Are you sure you want to change the base?
Conversation
rebase on latest GradedAxes set GradedAxes as a Sector dependency define fusion rules for simple categories pass test for simple categories
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1363 +/- ##
==========================================
+ Coverage 49.23% 57.49% +8.26%
==========================================
Files 110 114 +4
Lines 8320 8867 +547
==========================================
+ Hits 4096 5098 +1002
+ Misses 4224 3769 -455 ☔ View full report in Codecov by Sentry. |
Regarding the question of the SU(2) types, I believe we had settled on the following plan
|
gradedisequal(::AbstractUnitRange, ::OneToOne) = false | ||
gradedisequal(::OneToOne, ::AbstractUnitRange) = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't these be true if the AbstractUnitRange
runs from 1:1
and doesn't have any labels?
This is a work in progress for a full implementation of non-abelian fusion rules in
Sectors
. It also contains several patches on other components ofSectors
. A core aspect is that the dependency order betweenGradedAxes
andSectors
has been reversed:Sectors
now depends onGradedAxes
.To do:
CategoryProduct
SymmetryStyle
trait with valuesAbelianGroup
,NonAbelianGroup
andNonGroupSymmetry
To be decided:
c1 ⊗ c2
: either always aGradedUnitRange
or aGradedUnitRange
or aCategory
depending onSymmetryStyle
SU2
andSU{2}
.Decisions:
c1 ⊗ c2
: return type depends onSymmetryStyle
SU2
withSU{2}
and try to have a half-integer interface specific toSU{2}
Long term: how to handle braiding for fermions and anyons.